Online documentation - Websydian v6.5

Websydian Version 2.0 - What Is New

Since version 1.3, Websydian has gone through a number of substantial changes. Those being familiar with Websydian 1.3 will notice the following updates and features:

Websydian 2.0 is based on the new pattern libraries available with CA Plex version 3.5. All dependencies from Websydian to the old OBASE library have been removed.
The design of Websydian 2.0 has been organized in a modulized and layered design reflecting the architecture of the Sterling pattern libraries. Also the naming standards have been changed to reflect those of the Sterling libraries (names on edit points have been preserved to assure backward compatibility).
The Websydian main patterns - Page Generator, Event Handler, Dispatcher - have been split up in a number of 'building block patterns'. Features are selected by inheritance rather than by setting options.
The Document Template generation will now work with the Event Handler being scoped directly under the Page Generator functions. The template generation, though, will still work with the old Dummy Page structure.
A Utility module has been added to Websydian containing a WebEditDialog pattern analogous to the Sterling EditDialog pattern (similar to User maintained entity in OBASE).
The Utility module contains a pattern for including simple Java script functionality in the generated Document Templates. The included Java scripting will manage initialization of status fields.
Integrity Security validation and Session Management have been isolated in separate modules, and modules for User Management and Audit Control have been added.
A Shopping Cart pattern has been added to the Websydian portfolio as an add-on product. More modules will be available in the future.
The Websydian documentation has become integrated with the CA Plex 4.0 documentation. It is now possible to link directly to the documentation from Websydian library objects within a CA Plex model.

When upgrading a Websydian model from version 1.3 to version 2.0, a few actions need to be taken. See the technical paper Upgrade Guide to Version 2.0 for the detailed steps to be performed when migrating a Websydian model from version 1.3 to 2.0.